This forum is closed to new posts and
responses. The content has been migrated to the Digital Solutions Community. Please join us there for new content as well as this content. For customer support, please visit the official HCL customer support channels below:
Biggest problem is specially enabled stored forms, sent through email. It ends as a blank message. Embedded buttons & other programed niceties in a real workflow application, well they just dont exist in Outlook. Yhafta point users back into Notes with notes:// links thatll function somewhat less personalized for your users.
If you have emails that use hide-whens, they dont translate to Outlook.
When translating, Notes translates doclinks so SMTP ... that is, Exchange ... can deliver doclinks & dblinks if sent through. However, there are serious limitations.
If youre trying to copy out of Notes, then into Outlook, the doclinks/dblinks do not transfer via copy/paste. In fact its a ridiculous annoyance to convert:yhafta generate a notes:// link format for Outlook.
Also, just for the record,
-Outlook search is horrifically bad. Find a 3d party app, and fast.
-Microsoftll tell you themselves, keeping over 1000 emails in one folder is a loser. Outlooks slow & choppy.
-Dont try to operate on over 200 docs in one selection. Again, Outlook falls down, functioning slowly, often incompletely as your selection count increases above 200 emails.
-If your users hold emails longterm, youre asking for performance complaints. I generally shut down Outlook while using IM, or Notes. Even archiving docs after a month doesnt seem to help. I feel its the count of emails, not their size.
-Every couple of weeks Exchange / Outlook gets slow & choppy. Maybe thats the sheer number of people working in email at once, smaller outfits probably wont notice or think its them, personally.
-The larger the mailbox, youll notice Outlook does odd things every so often (1/month) with a random email. Cant tell, but it looks like the network isnt answering to every Outlook request, and Outlook responds, well, oddly when it gets random network dropouts communicating with Exchange. Emails hang in outbox, or dont get sent, or replies get sent when you had no chance to actually type in a reply.
But yknow, its the standard. Everyone suffers these same standard sillinesses.
On the Notes applications side, providing a forwarding email address in Notes Address Book to Exchange, that can cause issues. @NameLookup can translate to the original Notes ID in Notes, but the name fields that do address translations using the "address" checkboxes will shove the Exchange email into them. So any doc thats for access control, it has to be checked whether it is doing "address translation" (see the field checkboxes for translation). It cant do this anymore. @Namelookup is likely to be needed, & youll need to manually rewrite anything the address translation was helping with.
Id push back on using this forwarding address idea. Im not sure what could replace it though. Certainly dont allow them to replace the first FullName field value, thatll be fatal. See wha else theyve got.
Ive posted here with a tablet, so I have not added apostrophes for convenience. Dont take that as stupidity. ;)
Feedback response number WEBBADHUFF created by ~Sigmund Umwemanoni on 09/05/2016
Stored forms will die. More on the subject ...
Return to top
. . Stored forms will die. More on the ... (~Sigmund Umwema... 5.Sep.16) 
